Open
Conversation
JakubMastalerz
commented
Oct 16, 2025
tbx/project_styleguide/templates/patterns/pages/home/home_page.html
Outdated
Show resolved
Hide resolved
bmispelon
reviewed
Oct 16, 2025
tbx/project_styleguide/templates/patterns/navigation/components/breadcrumbs-jsonld.html
Outdated
Show resolved
Hide resolved
Tests were failing due to URL generation issues in test environment. Direct template rendering bypasses Wagtail URL resolution problems and provides more reliable test coverage for JSON-LD functionality.
Ensures Organization schema implementation is properly validated with tests for structure, social links, logo URL, and template inclusion. Prevents regression of homepage JSON-LD functionality.
Switched from apple-touch-icon.png (180x180) to android-chrome-512x512.png (512x512) for better rich results display and Google's recommended higher resolution. Follows Google PWA standards and provides better quality for search engine rich snippets. Standards followed: - Google PWA Manifest requirements: https://developers.google.com/web/fundamentals/web-app-manifest - Schema.org Organization logo recommendations: https://schema.org/Organization - Google Rich Results guidelines: https://developers.google.com/search/docs/appearance/structured-data/logo The 512x512px resolution exceeds Google's minimum requirement of 112x112px and follows PWA best practices for high-quality icon display.
- Move all imports to top of file - Remove redundant imports from test methods - Improve code organization and readability
- Add _extract_jsonld_by_type() helper to eliminate repetitive JSON-LD extraction - Add _get_organization_jsonld() helper for cleaner test methods - Reduce test_organization_jsonld_social_links from 30+ lines to 8 lines - All tests still pass with same coverage - Much more maintainable and readable
Collaborator
bmispelon
reviewed
Oct 29, 2025
Collaborator
bmispelon
left a comment
There was a problem hiding this comment.
I've left some suggestions for improvements, mostly in the tests.
I also notice that you're using a lot of inline imports rather than putting them all at the top of the file as is normally the case, was there a reason for that?
tbx/project_styleguide/templates/patterns/pages/blog/blog-posting-jsonld.html
Outdated
Show resolved
Hide resolved
Collaborator
No reason, just my rogue agent - apologies |
eca8020 to
c986e19
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Link to Ticket
Description of Changes Made
android-chrome-512x512.pngfollowing Google's recommendationsHow to Test
/<head>sectionhttps://torchbox.com/android-chrome-512x512.pngsameAsarrayfab run-testto ensure all tests passScreenshots
Expand to see more
The Organization JSON-LD appears in the page source as:
MR Checklist
Unit tests
Documentation
Browser testing
Data protection
Light and dark mode
Accessibility
Sustainability
Pattern library